We assume the parameters for the Dynamics NAV SQL server have already been set up correctly so the connection to the database has been established.
To configure the NAS
- Open the Dynamics NAV 2018 Administration tool. If it is not in the Start menu, you can locate it in the C:\Program Files (x86)\Microsoft Dynamics NAV\110\RoleTailored Client\ folder.
- Locate the Microsoft Dynamics NAV Server.msc file, and double-click it.
- Select the correct NAV service tier in the selection tree on the left side, and enter Edit mode.
General tab
Fill out the Services Default Company field. This field must be set for the NAS to start up correctly.
NAS Services tab
There are two methods to run the NAS: one for running only the KDS, and the other for running the KDS along with the Scheduler.
1: NAS running the KDS communication codeunit
For the NAS to run the communication between the Dynamics NAV system and the KDS, you need to enter 10001218 in the Startup Codeunit field. When this service starts, codeunit 10001218 KDS NAS will run. Codeunit 10001218 does not take any Startup Arguments nor Startup Method - both fields are left empty.
The KDS NAS codeunit will send the Kitchen Orders (KOTs) from the Dynamics NAVv to the KDS system, and it will also retrieve the Bump status on the preparation and expediter stations.
Codeunit 10001218 frequently calls codeunit 10001219 KDS Controller, which in turn calls codeunit 10001217 KDS Functions. These codeunits will update the status of the KOTs in the Dynamics NAV database, thus making it possible to see the status of the KDS system on the Hospitality POS.
2: NAS running the KDS system and the LS Retail Scheduler
It is not recommended to have the NAS service that runs the KDS communication do other chores.
If you also want NAS to run the LS Nav Scheduler, you must enter these setup values:
| Startup Codeunit | 99001454 |
| Startup Method | LSRetailNASHandler |
| Startup Arguments | KDS LSRSCHEDULER NASID,TYPEFILTER=HOSP,LOG=1,REPEAT=1 |
Codeunit 99001454 LS Retail NAS Handler can start the KDS system and also run other tasks, such as the LS Retail Scheduler, the LS Retail Batch Posting system, and the standard Job Queue system.
The Startup Argument in the example above will start the KDS communication and also start the LS Retail Scheduler, where it will run all the Scheduler Jobs that have HOSP in the Scheduler Job Type Code field. Note: A space will separate the keywords in the Startup Argument.
Codeunit 99001454 will recognize the following keywords in the Startup Argument:
- KDS which will start the communication between Dynamics NAV and the KDS system.
- LSBATCHPOST, which will run the LS Retail Batch Posting Queue.
- JOBQUEUE, which will run the standard Job Queue.
- LSRSCHEDULER, which will run the LS Retail Scheduler.
Only the LSRSCHEDULER takes parameters, so if you want to include that codeunit in the Startup Arguments, put it in the last position in the Startup Argument string.
Here is an example of how the Startup Argument could look, if both the KDS, LS Retail Scheduler, and the Batch Posting Queue are to be started by the NAS:
KDS BATCHPOST LSRSCHEDULER NASID,TYPEFILTER=HOSP,LOG=1,REPEAT=1
After saving the configuration, restart the NAS service tier and check the Event Log Viewer for possible errors the NAS may have encountered. Typical problems are, for example, if the Log On user on the service is not a Dynamics NAV user, or the Service default company is missing or wrong.